[Release] Bump version to 0.18.0#115
Conversation
…edentialUpdate feature
There was a problem hiding this comment.
Wait — the date 03-July-2026 and 26-June-2026 actually use the same DD-Month-YYYY format. Let me reconsider whether there's a real inconsistency.
Both use DD-Month-YYYY, so the format is actually consistent. The suggestion I posted is incorrect (it also changes "July" to "June" which is wrong). This is not a real issue.
The PR is a clean, consistent version bump. All three files (package.json, package-lock.json, CHANGELOG.md) are aligned on 0.18.0, the changelog entry is properly formatted, and the CAP Operator version requirement note is now correctly using ### heading style matching the surrounding structure. No substantive issues found — the previously posted comment was a false positive and can be dismissed.
PR Bot Information
Version: 1.26.14
- Correlation ID:
deccaf20-76cf-11f1-89e8-4fd8b10d944e - LLM:
anthropic--claude-4.6-sonnet - Event Trigger:
pull_request.opened - File Content Strategy: Full file content
Release: Bump Version to 0.18.0
🔖 Chore: Bumps the
@cap-js/cap-operator-pluginpackage version from0.17.0to0.18.0and updates the changelog with the new release entry.Changes
CHANGELOG.md: Added release notes forv0.18.0(03-July-2026), noting compatibility with CAP Operatorv0.32.0or later. Documents the newrolloutOnCredentialUpdatefield added toCAPApplicationspec. Also minor formatting fix for thev0.17.0heading.package.json: Bumped version from0.17.0to0.18.0.package-lock.json: Updated lock file to reflect the new version0.18.0.What's New in 0.18.0
✨ Added
rolloutOnCredentialUpdatefield toCAPApplicationspec — when enabled, workloads are automatically redeployed when their service credentials are updated.v0.32.0or later.🔄 Regenerate and Update Summary
PR Bot Information
Version:
1.26.14anthropic--claude-4.6-sonnetdeccaf20-76cf-11f1-89e8-4fd8b10d944epull_request.opened